About three weeks ago the verify for the Public Folder Databases starting failing when verifying a single log file. I worked with Symantec yesterday who said this would be support issue with Microsoft and to contact Microsoft Support to run the ISINTEG utility. Below is the error information received. They are running Exchange 2007 on Server 2008 Standard Service Pack 2 64 bit. We are backing up using Symantec Backup Exec 2010 and it had been working for years before three weeks ago. Job ended: Monday, December 06, 2010 at 9:05:34 PM Completed status: Failed Final error: 0xe000fedf - A failure occurred reading an object. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-65247 Backup- \\DHDC.corp.dynamichomes.com\Microsoft Information Store\Second Storage Group WARNING: "\\DHDC.corp.dynamichomes.com\Microsoft Information Store\Second Storage Group\Logs ( E01000069E0.log - E0100006C94.log )" is a corrupt file. This file cannot verify. Any help would be appreciated. Thank you.

Hi Chad, Is it possible to use Windows Server Backup to backup the database to test? Can you find the logs E01000069E0.log ~ E0100006C94.log in the log directory? You can dismount the database and move all log files and .chk file to another folder, then mount the database with new set of log files and make a new backup. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Chad, Any updates?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Frank, We are using Symantec Backup Exec 2010 to backup the Server data and Exchange Databases. I have not tried to dismount the database yet. I will have to log back into the server and see if E01000069E0.log ~ E0100006C94.log are in the log directory. Are those just log files or are those actually part of the database? Sorry it took so long to get back to you. Please let me know your suggestion at your earliest convenience. Thanks. Chad

Hi Frank, Found out the issue was with data corrpution between the 2 OS drives that were configured as RAID. We had another hard drive fail and after the new drive was rebuilt the data was verified and we have not had a problem with it since. Thank you for your help. Please go ahead and close the post. Chad